Account entity location based navigation and display for a projectable transaction card

ABSTRACT

A device may determine information that identifies a location of a projectable transaction card. The device may determine that the location of the projectable transaction card is in proximity to a location associated with an account entity. The device may determine navigation information based on determining that the location of the projectable transaction card is in proximity to the location associated with the account entity. The navigation information includes information for navigating from the location of the projectable transaction card to the location associated with the account entity. The device may provide the navigation information for display on a display screen of the projectable transaction card. The navigation information is not provided for display on the display screen of the projectable transaction card prior to the location of the projectable transaction card being in proximity to the location associated with the account entity.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/742,405, filed Jan. 14, 2020 (now U.S. Pat. No. 10,997,589), which isincorporated herein by reference in its entirety.

BACKGROUND

A user of a transaction card associated with an account entity may wantto locate an automated teller machine (ATM), a branch of a financialinstitution, and/or another location associated with the account entity.For example, the location may provide a way for the user to transact(e.g., deposit, withdraw, or pay a bill) with the account entity via thetransaction card.

SUMMARY

According to some implementations, a method may include determining, bya device, information that identifies a location of a projectabletransaction card, wherein the projectable transaction card is associatedwith an account entity, and wherein the projectable transaction card isassociated with a user account associated with the account entity;determining, by the device, that the location of the projectabletransaction card is in proximity to a location associated with theaccount entity; determining, by the device, navigation information basedon determining that the location of the projectable transaction card isin proximity to the location associated with the account entity, whereinthe navigation information includes information for navigating from thelocation of the projectable transaction card to the location associatedwith the account entity; and providing, by the device, the navigationinformation for display on a display screen of the projectabletransaction card, wherein the navigation information is not provided fordisplay on the display screen of the projectable transaction card priorto the location of the projectable transaction card being in proximityto the location associated with the account entity.

According to some implementations, a device may include one or morememories; and one or more processors, communicatively coupled to the oneor more memories, configured to: identify a location of a projectabletransaction card associated with an account entity, wherein theprojectable transaction card is associated with a user accountassociated with the account entity; determine that the location of theprojectable transaction card is within at least one of: a thresholddistance of a location associated with the account entity, or ageographical area associated with the location of the account entity;determine navigation information for navigating from the location of theprojectable transaction card to the location associated with the accountentity, wherein the navigation information is determined based on thelocation of the projectable transaction card being within the thresholddistance or within the geographical area; and provide the navigationinformation for display on a display screen of the projectabletransaction card, wherein the navigation information is not provided fordisplay on the display screen of the projectable transaction card priorto the location of the projectable transaction card being within thethreshold distance or within the geographical area.

According to some implementations, a non-transitory computer-readablemedium may store one or more instructions. The one or more instructions,when executed by one or more processors of a device, may cause the oneor more processors to: determine that a location of a projectabletransaction card is in proximity to a location associated with anaccount entity; wherein the projectable transaction card is associatedwith the account entity, and wherein the projectable transaction card isassociated with a user account associated with the account entity;determine navigation information based on determining that the locationof the projectable transaction card is in proximity to the locationassociated with the account entity, wherein the navigation informationincludes information for navigating from the location of the projectabletransaction card to the location associated with the account entity; andprovide the navigation information for display on a display screen ofthe projectable transaction card, wherein the navigation information isnot provided for display on the display screen of the projectabletransaction card prior to the location of the projectable transactioncard being in proximity to the location associated with the accountentity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIGS. 4-6 are flowcharts of example processes for account entitylocation based navigation and display for a projectable transactioncard.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A transaction card may be associated with a user account, which is alsoassociated with an account entity, such as a bank or other financialinstitution. The user may want to find a location associated with theaccount entity, such as an ATM or a branch of a financial institution,so that the user can transact with the account entity. However, the usermay be unaware of the location and/or may be unaware of directions toarrive at the location. In some instances, the user may have a need togo to the location, but may forget about the need when the user is nearthe location.

With advancements in transaction card technology, a transaction card maybe a projectable transaction card. A projectable transaction card is adevice, capable of being used to conduct a transaction, that includes adisplay (e.g., a display screen) that can be used to display information(e.g., to a user). Information provided for display via the display ofthe projectable transaction card may be dynamic and, therefore, can bemodified, updated, customized, and/or the like. For example, a displayof a projectable transaction card can be updated to display an accountidentifier, transaction indicator, a name of an account holderassociated with the projectable transaction card, and/or the like.

A projectable transaction card may also include a communicationinterface that enables the projectable transaction card to receiveinformation over a wireless network, such as a wirelesstelecommunications network, a Wi-Fi network, and/or the like. Theinformation may include information for display via the display of theprojectable transaction card. The communication interface may alsoenable the projectable transaction card to transmit information over thewireless network, such as a selection related to information receivedover the wireless network.

Some implementations described herein provide techniques and apparatusesassociated with providing navigation information for display on adisplay screen of a projectable transaction card. In someimplementations, a navigation device provides the navigation informationbased on determining that the projectable transaction card is within athreshold distance from a location associated with an account entity orwithin a geographical area associated with the location associated withthe account entity. The location associated with the account entity maybe, for example, a location of an ATM or a branch of a financialinstitution that issued the projectable transaction card.

By providing navigation information for display on a projectabletransaction card based on proximity to a location associated with theaccount entity, a user may be reminded to transact with the accountentity and may be provided with information for navigating to a locationat which the user may be able to perform a transaction. These techniquesmay reduce computing resources (e.g., processor resources, memoryresources, communication resources, and/or the like) that mightotherwise be consumed in response to late payments, account overdrafts,and/or the like.

The techniques may also reduce consumption of computing resources thatmight otherwise be consumed by using a mobile computing device, such asa mobile phone, to access a navigation application, search for locationsassociated with the account entity, select a desired location associatedwith the account entity, and request information for navigating to thedesired location associated with the account entity. The techniques mayalso be helpful when a mobile computing device is unavailable.

The techniques may also provide a dedicated display for displaying theinformation for navigating to the location associated with the accountentity. This may free up computing resources of another device so thatthe other device can be used for other operations. For example, a usermay employ the other device to display a video for a child while usingthe projectable transaction card to display information for navigatingto the location associated with the account entity.

In some implementations, the navigation device may provide thenavigation information based on additional factors. For example, whendetermining to provide the navigation information, the navigation devicemay consider user preferences, which may be received, for example, via aweb interface accessible to the user via a user device, or via anapplication local to the user device. Additionally, or alternatively,when determining to provide the navigation information, the navigationdevice may consider historical information, such as information relatingto prior transactions between the user and the account entity via theprojectable transaction card. In some implementations, when determiningto provide the navigation information, the navigation device mayconsider information relating to the user account, such as an upcomingbilling due date, a low or high balance for the user account, and/or thelike.

In some implementations, when determining to provide the navigationinformation, the navigation device may provide a prompt to a user deviceto request input regarding whether the navigation device should providethe navigation information. The navigation device may provide or notprovide the navigation information based on the input. In addition tobeing a basis for providing navigation information for display to theuser, the prompt may also be used as a security measure, such that theuser may receive a prompt whenever the projectable transaction card isin proximity to a location associated with the account entity. Forexample, if a projectable transaction card is stolen, the user mayreceive the prompt, via a user device, that the projectable transactioncard is in proximity to an account entity and may be used tofraudulently transact with the account entity. The user may provideinput to alert the account entity that a stolen projectable transactioncard is in proximity to a location associated with the account entity.Because the account entity may have a security camera, a fraudulenttransaction may be prevented, or a malicious actor may be identifiedusing an image from the security camera. In this way, computingresources may be conserved that otherwise might have been used toidentify, investigate, and recover from such fraudulent transactionand/or identity theft.

FIGS. 1A-1C are diagrams of one or more example implementations 100described herein. As shown in FIGS. 1A-1C, the example implementation(s)100 may include a projectable transaction card and a navigation device.

The projectable transaction card may be associated with an accountentity, such as a card issuer and/or a financial institution. Theprojectable transaction card may also be associated with a user accountthat is associated with the account entity. In some implementations, theprojectable transaction card may provide a method for transacting withthe account entity associated with the user account. For example, a usermay present the projectable transaction card to a merchant, which canthen receive payment from the account entity using the projectabletransaction card. The account entity may associate the payment with theuser account to reconcile the payment.

The account entity may include one or more account access points, suchas ATMs, branches of the account entity, and/or other locationsassociated with the account entity. A user may be able to present theprojectable transaction card at a location associated with the accountentity to transact using the user account. For example, the user maywithdraw or deposit currency and/or notes, transfer funds betweenaccounts, and/or the like at the location associated with the accountentity.

As shown in FIG. 1A, and by reference number 105, the navigation devicemay receive location information associated with the projectabletransaction card. For example, the location information may includeinformation derived from a network, such as a global positioning systemnetwork, a local area network, a wide area network, and/or the like,received at the projectable transaction card or a nearby user device(e.g., a mobile phone). The location information associated with theprojectable transaction card may provide information regarding alocation of the projectable transaction card, a user, and/or a nearbydevice relative to one or more other locations.

In some implementations, the navigation device may receive the locationinformation from the projectable transaction card in response to userinput at the projectable transaction card or a user device. For example,the projectable transaction card may receive input from a user totransmit the location information to the navigation device.Additionally, or alternatively, a nearby user device may receive inputfrom a user to transmit the location information to the navigationdevice.

In some implementations, a remote device that is not nearby may receiveinput from a user to transmit the location information to the navigationdevice. For example, a user that has access to the user account (e.g., aspouse or parent of the nearby user) may request, via the remote device,transmission of the location information associated with the projectabletransaction card to the navigation device. The user that has access tothe user account may transmit the request via an application interface,for example. The request may be transmitted to the projectabletransaction card, a nearby user device, the navigation device, and/orthe like. If the request is transmitted to the navigation device, thenavigation device may transmit a request for location information to theprojectable transaction card, a nearby user device, and/or the like.

In some implementations, the navigation device may receive the locationinformation associated with the projectable transaction card based onuser preferences associated with the projectable transaction card, auser account, and/or the like. For example, the user preferences mayspecify triggers for transmitting the location information, such asexpiration of a time interval between iterations of transmittinglocation information associated with the projectable transaction card,arriving at a scheduled transmission time, entering within a thresholddistance between the projectable transaction card and an account entitylocation, entering within a geographical area, and/or the like. In someimplementations, the user preferences may include one or more triggersassociated with a status of another device, such as battery status,availability of a display, location, and/or the like.

In some implementations, the navigation device may receive, or haveaccess to, user preferences received via a web interface accessible tothe user via a user device or via an application local to the userdevice. In some implementations, user preferences may be derived basedon historical actions taken by the user. For example, the navigationdevice or another device may use one or more machine learning techniquesto generate a model for predicting conditions under which a user prefersto send location information associated with the projectable transactioncard. Some example machine learning techniques, which may be used forthis purpose, are discussed below.

As shown by reference number 110, the navigation device may determinewhether the location of the projectable transaction device is withinproximity to a location associated with an account entity (“accountentity location”). In some implementations, the navigation deviceaccesses information that identifies one or more account entitylocations to determine if one or more of the account entity locations iswithin proximity to a location of the projectable transaction card, asindicated in the location information. In some implementations, thenavigation device may further identify a type of the account entitylocation. In some implementations, the navigation device may filteraccount entity locations by type and provide the navigation informationif the projectable transaction card is in proximity of an unfilteredlocation type (e.g., a type of location that passes through the filter,rather than being filtered out). As an example, the location type mayindicate that a location includes one or more of a location of a branchof a financial institution, an ATM, an eatery associated with afinancial institution or issuer of the projectable transaction card,and/or the like. By filtering account entity locations by type, thenavigation device conserves computing resources that would otherwise beused to process all types of account entity locations.

In some implementations, the navigation device may access informationthat identifies one or more preferred account entity locations or types,according to user preferences or a location associated with the useraccount, to determine if the projectable transaction card is withinproximity to a preferred account entity location or type. By using userpreferences, the navigation device conserves computing resources thatwould otherwise be used to process all account entity locations ortypes.

In some implementations, when determining whether the projectabletransaction card is in proximity to a location associated with theaccount entity, the navigation device may determine if the projectabletransaction card is within at least one of a threshold distance of thelocation associated with the account entity, a threshold estimatedtravel time of the location associated with the account entity, or ageographical area associated with the location associated with theaccount entity.

In some implementations, the user may specify (e.g., in userpreferences) the threshold to be used for determining whether theprojectable transaction card is in proximity to the location associatedwith the account entity. In this way, computing resources may beconserved, which might have otherwise been used for determining,generating, and/or providing navigation information when such navigationinformation is less likely to be useful because the projectabletransaction card is not close enough, based on the user's owndefinition, to the location associated with the account entity.

In some implementations the navigation device may specify the thresholdto be used for determining whether the projectable transaction card isin proximity to the location associated with the account entity. In someimplementations, the threshold may be a predetermined threshold. In someimplementations, the threshold may be based on relationships betweenhistorical activity information associated with the user account andhistorical location information associated with the projectabletransaction card and/or historical location information associated withan account entity location. In some implementations, these relationshipsmay be determined using machine learning, such as one or more of themachine learning techniques described herein.

By determining that the projectable transaction card is in proximity toa location associated with an account entity, the navigation device maydetermine occasions when providing navigation information may be usefulto a user of the projectable transaction card. In this way, computingresources may be conserved, which may otherwise have been used fordetermining, generating, and/or providing navigation information whensuch navigation information is less likely to be useful because theprojectable transaction card is not in proximity to an account entitylocation.

As shown in FIG. 1B, and by reference number 115, the navigation devicedetermines navigation information for navigating to the locationassociated with the account entity. In some implementations, thenavigation device may determine the navigation information based, atleast in part, on determining that the location of the projectabletransaction card is in proximity to the location associated with theaccount entity. By determining the navigation information when thelocation of the projectable transaction card is in proximity to thelocation associated with the account entity, the navigation deviceconserves computing resources that would otherwise be used to determinenavigation information for locations that are not in proximity to thelocation of the projectable transaction card and are unlikely to be ofinterest to the user.

The navigation information may include information for navigating fromthe location of the projectable transaction card to the locationassociated with the account entity. In some implementations, thenavigation information may include a list of steps of directions fordisplay, a static or dynamic map for display, and/or the like.Additionally, or alternatively, the navigation information may includenavigation information for presenting information via another outputcomponent, such as a speaker of the projectable transaction card. Forexample, the navigation information may provide directions fornavigating from the location of the projectable transaction card to thelocation associated with the account entity, which directions may bepresented via audible prompts for upcoming steps of the directions(e.g., an upcoming turn or a distance to remain on a current path).

In some implementations, the navigation device may determine whether todetermine the navigation information or to provide the navigationinformation to the projectable transaction card. For example, thenavigation device may determine whether to determine or provide thenavigation information based on identifying a type of the locationassociated with the account entity. In some implementations, thenavigation device may filter locations associated with the accountentity by type, and provide the navigation information to theprojectable transaction card only if the location associated with theaccount entity is an unfiltered type (e.g., is not filtered out based ontype). Additionally, or alternatively, the navigation device maydetermine whether to determine or provide the navigation informationbased on whether an upcoming due date, associated with the user account,is within a time threshold. In some of these implementations, thenavigation device may determine, or gain access to a determination, ofan upcoming due date.

In some implementations, the navigation device determines whether todetermine or provide the navigation information based on determining, orgaining access to a determination regarding, historical activityinformation associated with the user account. The navigation device maythen determine, or gain access to a determination by another device,that activity associated with the user account is expected based on thehistorical activity information. The determination may be made usingmachine learning, as discussed below.

As described herein, the navigation device may use one or moreartificial intelligence techniques, such as machine learning, deeplearning, and/or the like to determine whether activity associated withthe user account (hereinafter referred to as “account activity”) isexpected. In some implementations, the navigation device may include anaccount activity platform. In some implementations, the navigationdevice may access an account activity platform on another device and/orreceive determinations by the account activity platform on the otherdevice.

In some implementations, the account activity platform may parse naturallanguage descriptions of parameters of historical transactions. Forexample, the account activity platform may obtain data identifying, innatural language, descriptions of timings, locations, amounts, types,and/or the like of historical transactions, and may parse the data toidentify indicators relating to patterns of account activity, and/or thelike.

In some implementations, the account activity platform may determine acharacteristic of a historical transaction based on natural languageprocessing of a description of the historical transaction, which mayinclude a description of characteristics and/or conditions of thehistorical transaction. For example, based on a description of ahistorical account activity including “Dec. 5, 2018 deposit of $1,000 atWashington St. branch”, the account activity platform may use naturallanguage processing to determine that characteristics of the historicaltransaction include that the historical transaction was a deposit, thehistorical transaction was performed on the 5^(th) day of the month, andthe historical transaction was performed at a particular branch of afinancial institution. In this case, the account activity platform maydetermine that a natural language text corresponds to an indicator of apattern of account activity based on data relating to other historicalaccount activity, data relating to events of the account (e.g., a billdue date), and/or the like. For example, if historical accountactivities indicate that the user account often makes a large deposit onor around the 5^(th) day of the month, the account activity platform maydetermine a pattern of account activity. The account activity platformmay then determine that if a current date is on or around the 5^(th) dayof a month, an increased likelihood of upcoming account activity exists.One or more such factors may be weighted in a determination of whetheraccount activity is expected.

In this way, the account activity platform may identify characteristicsof historical account activities to determine whether account activityis expected, as described herein. Based on applying a rigorous andautomated process associated with identifying characteristics ofhistorical account activities, the account activity platform enablesrecognition and/or identification of thousands or millions ofcharacteristics of account activities for thousands or millions oftransactions, thereby increasing an accuracy and consistency ofdetermining whether account activity is expected relative to requiringcomputing resources to be allocated for hundreds or thousands oftechnicians to manually determine whether account activity is expectedbased on thousands or millions of characteristics of historical accountactivities.

In some implementations, the account activity platform may determinewhether a characteristic of a historical transaction, other events ofthe account, and/or the like is or can be an indicator of a pattern ofaccount activity or an indicator of whether account activity isexpected, as described herein. For example, the account activityplatform may determine whether one or more current conditions of a useraccount (e.g., characteristics of one or more recent transactions, apast or upcoming account event, and/or the like) associated with theaccount entity is the same or similar to one or more conditions of oneor more historical transactions, or if account activity can be expectedbased on a pattern of historical account activity.

A characteristic of one or more historical transactions can be comparedwith current conditions to determine whether account activity isexpected. In this case, the account activity platform may generate amodel of expected account activity. For example, the account activityplatform may train a model using information that includes informationrelating to a plurality of characteristics of historical transactions, aplurality of historical account events, and/or the like, to determineconditions under which account activity is expected. As an example, theaccount activity platform may determine that past conditions areassociated with a threshold probability of being associated withexpected account activity. In some implementations, the account activityplatform may use a scoring system (e.g., with relatively high scoresand/or relatively low scores) to identify and/or classify conditions, orone or more characteristics of conditions, as being associated withexpected account activity. In this case, the account activity platformmay determine that a relatively high score (e.g., as being likely to beidentified) is to be assigned to characteristics of a recenttransaction, an account event, and/or other conditions that aredetermined to be the same or similar as previously identifiedcharacteristics of recent transactions, account events, and/or otherconditions that were followed by account activity (or more frequentlyidentified than past identified transactions, account events, and/orother conditions). In contrast, the account activity platform maydetermine that a relatively low score (e.g., as being unlikely to beidentified) is to be assigned to characteristics of recent transactions,account events, and/or other conditions that are determined to bedifferent than past identified recent transactions, account events,and/or other conditions that were followed by account activity (or lessfrequently identified than past identified characteristics).

In some implementations, the account activity platform may perform adata preprocessing operation when generating the model of expectedaccount activity. For example, the account activity platform maypreprocess data (e.g., a description of a timing, a location, an amount,a type, and/or the like of a transaction, account events, and/or thelike) to remove non-ASCII characters, white spaces, confidential dataand/or the like. In this way, the account activity platform may organizethousands, millions, or billions of data entries for machine learningand model generation.

In some implementations, the account activity platform may perform atraining operation when generating the model of expected accountactivity. For example, the account activity platform may portionreceived information relating to a description of a timing, a location,an amount, a type, and/or the like of a transaction, associations withother transactions or account events, and/or the like into a trainingset (e.g., a set of data to train the model), a validation set (e.g., aset of data used to evaluate a fit of the model and/or to fine tune themodel), a test set (e.g., a set of data used to evaluate a final fit ofthe model), and/or the like. In some implementations, the accountactivity platform may preprocess and/or perform dimensionality reductionto reduce the received information relating to a description of atiming, a location, an amount, a type, and/or the like of a transaction,associations with other transactions or account events, and/or the liketo a minimum feature set. In some implementations, the account activityplatform may train the model of expected account activity on thisminimum feature set, thereby reducing processing to train the machinelearning model, and may apply a classification technique, to the minimumfeature set.

In some implementations, the account activity platform may use aclassification technique, such as a logistic regression classificationtechnique, a random forest classification technique, a gradient boostingmachine learning (GBM) technique, and/or the like, to determine acategorical outcome (e.g., that account activity is expected, thataccount activity is not expected, and/or the like). Additionally, oralternatively, the account activity platform may use a naïve Bayesianclassifier technique. In this case, the account activity platform mayperform binary recursive partitioning to split the data of the minimumfeature set into partitions and/or branches and use the partitionsand/or branches to perform predictions (e.g., that account activity isor is not expected). Based on using recursive partitioning, the accountactivity platform may reduce utilization of computing resources relativeto manual, linear sorting and analysis of data points, thereby enablinguse of thousands, millions, or billions of data points to train a model,which may result in a more accurate model than using fewer data points.

Additionally, or alternatively, the account activity platform may use asupport vector machine (SVM) classifier technique to generate anon-linear boundary between data points in the training set. In thiscase, the non-linear boundary is used to classify test data (e.g., datarelating conditions of a user account into a particular class (e.g., aclass indicating that account activity is expected, a class indicatingthat the account activity is not expected, and/or the like).

Additionally, or alternatively, where the test data includes image data,video data, and/or the like, the account activity platform may use acomputer vision technique, such as a convolutional neural networktechnique to assist in classifying test data (e.g., data relatingconditions of a user account) into a particular class (e.g., a classindicating that the account activity is expected, a class indicatingthat the account activity is not expected, and/or the like). In somecases, the computer vision technique may include using an imagerecognition technique (e.g., an Inception framework, a ResNet framework,a Visual Geometry Group (VGG) framework, and/or the like), an objectdetection technique (e.g. a Single Shot Detector (SSD) framework, a YouOnly Look Once (YOLO) framework, and/or the like), an object in motiontechnique (e.g., an optical flow framework and/or the like), and/or thelike.

Additionally, or alternatively, the account activity platform may trainthe model of expected account activity using a supervised trainingprocedure that includes receiving input to the model from a subjectmatter expert, which may reduce an amount of time, an amount ofcomputing resources, and/or the like to train the model of expectedaccount activity relative to an unsupervised training procedure. In someimplementations, the account activity platform may use one or more othermodel training techniques, such as a neural network technique, a latentsemantic indexing technique, and/or the like. For example, the accountactivity platform may perform an artificial neural network processingtechnique (e.g., using a two-layer feedforward neural networkarchitecture, a three-layer feedforward neural network architecture,and/or the like) to perform pattern recognition with regard to patternsof whether or not conditions of a user account described using differentsemantic descriptions can be used to determine whether account activityis expected. In this case, using the artificial neural networkprocessing technique may improve an accuracy of a model (e.g., the modelof expected account activity) generated by the account activity platformby being more robust to noisy, imprecise, or incomplete data, and byenabling the account activity platform to detect patterns and/or trendsundetectable to human analysts or systems using less-complex techniques.

As an example, the account activity platform may use a supervisedmulti-label classification technique to train the model. For example, asa first step, the account activity platform may map conditions of a useraccount to account activity. In this case, the conditions may becharacterized as indicating account activity or not indicating accountactivity based on characteristics of the conditions (e.g., whethertiming until an upcoming bill is due is similar or associated withtiming until a past bill that resulted in account activity). As a secondstep, the account activity platform may determine classifier chains,whereby labels of target variables may be correlated (e.g., in thisexample, labels may be a timing, a location, an amount, a type, and/orthe like of a transaction, account events, and/or the like andcorrelation may refer to a common condition characteristic of a timing,a location, an amount, a type, and/or the like of a transaction, accountevents, and/or the like). In this case, the account activity platformmay use an output of a first label as an input for a second label (aswell as one or more input features, which may be other data relating tothe condition of a user account), and may determine a likelihood thatparticular conditions of a user account, that includes a set ofcharacteristics, are associated with expected account activity based ona similarity to other conditions that include similar characteristicsthat are associated with account activity. In this way, the accountactivity platform transforms classification from amultilabel-classification problem to multiple single-classificationproblems, thereby reducing processing utilization. As a third step, theaccount activity platform may determine a Hamming Loss Metric relatingto an accuracy of a label in performing a classification by using thevalidation set of the data. For example, an accuracy with which aweighting applied to each characteristic of conditions of a user accountand whether each characteristic is associated with expected accountactivity or not, results in a prediction of whether the expected accountactivity can correctly be determined, thereby accounting for differingamounts to which association of any one characteristic influencesdetermination of expected account activity. As a fourth step, theaccount activity platform may finalize the model based on labels thatsatisfy a threshold accuracy associated with the Hamming Loss Metric andmay use the model for subsequent prediction of whether conditions of auser account are to result in the determination of expected accountactivity.

As another example, the account activity platform may determine, using alinear regression technique, that a threshold percentage ofcharacteristics of conditions of a user account, in a set ofcharacteristics, do not result in expected account activity, and maydetermine that those characteristics are to receive relatively lowassociation scores. In contrast, the account activity platform maydetermine that another threshold percentage of characteristics ofconditions of a user account result in expected account activity, andmay assign a relatively high association score to those characteristics.Based on the characteristics resulting in expected activity or not, theaccount activity platform may generate the model of expected accountactivity and may use the model of expected account activity foranalyzing new conditions of a user account, and/or the like that theaccount activity platform identifies.

In some implementations, a different device, such as a server device,may generate and train the model. The different device may send themodel for use by the account activity platform. The different device mayupdate and send (e.g., on a scheduled basis, on an on-demand basis, on atriggered basis, on a periodic basis, and/or the like) the model to theaccount activity platform.

Accordingly, the account activity platform may use any number ofartificial intelligence techniques, machine learning techniques, deeplearning techniques, and/or the like to determine whether activityassociated with a user account is expected.

As shown by reference number 120, the navigation device may provide thenavigation information to the projectable transaction card. In someimplementations, the navigation device may provide the navigationinformation based on one or more factors, which may include adetermination that the projectable transaction card is in proximity to alocation associated with the account entity (e.g., within a thresholddistance of and/or within a geographical area associated with theaccount entity location), an identification of a type of the accountentity location, an indication received via the projectable transactioncard or a nearby user device that the navigation information is desiredby the user, expected activity associated with a user account based onhistorical activity information, and/or the like.

For example, the navigation device may provide, for display or otheroutput, a user interface associated with whether to display or outputthe navigation information. In some implementations, the user interfacemay be provided via the projectable transaction card. In someimplementations, the user interface may be provided via a nearby userdevice, such as a mobile phone. In some implementations, the userinterface may be provided via a local application associated with theaccount entity, a messaging application, an interactive webpage, and/orthe like. For example, the navigation device may determine that theprojectable transaction card is in proximity to a location associatedwith the account entity, provide a user interface to request inputregarding whether to display the navigation information at theprojectable transaction card, and then provide or not provide thenavigation information to the projectable transaction card based on anindication of the input.

As shown by reference number 125, the projectable transaction card maydisplay the navigation information. Although the illustratedimplementation(s) 100 shows the navigation information being presentedvia a display, the navigation information may additionally oralternatively be presented via another type of output component, such asa speaker of the projectable transaction card or another type oftransaction card.

By providing the navigation information to the projectable transactioncard for display on the display of the projectable transaction card,computing resources of a nearby user device may be conserved. Forexample, a display of the nearby user device may be used to displayother information or not display any information.

As shown by FIG. 1C, information displayed on a display of theprojectable transaction card may dynamically change. For example, theprojectable transaction card may change to display navigationinformation from displaying an account identifier, a transactionindicator, a name of the account holder, and/or the like, where thenavigation information is not provided for display on the display screenof the projectable transaction card prior to the location of theprojectable transaction card being in proximity to the account entitylocation.

In some implementations, the navigation information may be displayed asone or more of alphanumeric characters providing one or more steps fordirections, a map including a part or entirety of a route to the accountentity location, and/or symbols (e.g., arrows and/or the like).

In some implementations, the navigation device may determine (e.g., viaan update from the projectable transaction card) information thatidentifies an updated location of the projectable transaction card. Thenavigation device may determine that the updated location is not inproximity to the location associated with the account entity. Based onthis determination, the navigation device may cause the navigationinformation to stop being displayed on the display screen of theprojectable transaction card. This may conserve computing resourcesincluding those that would otherwise be used to display the navigationinformation at the projectable transaction card, communicate updates ofdirections to the projectable transaction card, receive updates oflocations from the projectable transaction card, and/or the like.

As indicated above, FIGS. 1A-1C are provided as one or more examples.Other examples may differ from what is described with regard to FIGS.1A-1C.

For example, in some implementations, the projectable transaction cardmay be location aware. The projectable transaction card may also beconfigured with identifications of one or more locations associated withthe account entity that is associated with the projectable transactioncard, such that the projectable transaction card may detect when theprojectable transaction card is in proximity to a location associatedwith the account entity. The projectable transaction card may haveaccess (e.g., local access) to a set of maps, or other location data,and may be able to determine navigation information based on determiningthat the location of the projectable transaction card is in proximity tothe location associated with the account entity.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG. 2, environment 200 may include a projectable transaction card 210, anavigation device 220, a user device 230, an entity location device 240,and a network 250. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

Projectable transaction card 210 includes a transaction card capable ofdisplaying information via a display, as described herein. In someimplementations, projectable transaction card 210 is capable ofcommunicating with one or more other devices of environment 200 (e.g.,via Bluetooth communication, communication, Wi-Fi communication, a nearfield communication session, via a cellular network, and/or the like).Projectable transaction card 210 is capable of communicating data for atransaction and/or information that identifies a location of theprojectable transaction card. For example, projectable transaction card210 may communicate data including a virtual transaction number,transaction card identification information (e.g., an accountidentifier, a cardholder identifier, and/or the like), accountinformation, banking information, and/or the like, associated withperforming a transaction. For example, to communicate the data,projectable transaction card 210 may include a magnetic strip and/or anintegrated circuit (IC) chip (e.g., a EUROPAY®, MASTERCARD®, VISA® (EMV)chip).

Projectable transaction card 210 may include a display (e.g., a displayscreen) that can be used to display information. Information providedfor display via the display of projectable transaction card 210 may bedynamic and, therefore, can be modified, updated, customized, and/or thelike. For example, a display of projectable transaction card 210 can beupdated to display a visual representation of navigation information. Insome implementations, projectable transaction card 210 includes one ormore other output components that may be configured to dynamicallypresent information. For example, projectable transaction card 210 mayinclude a speaker that can dynamically present audible information.

Projectable transaction card 210 may also include a communicationinterface that enables projectable transaction card 210 to receiveinformation over a network, such as a wireless telecommunicationsnetwork, a Wi-Fi network, and/or the like. In some implementations, theinformation may include information for display via the display of theprojectable transaction card. The communication interface may alsoenable projectable transaction card 210 to transmit information overnetwork 250, such as information that identifies a location ofprojectable transaction card 210 and/or information that indicates userinput regarding whether navigation information is to be displayed byprojectable transaction card 210.

In some implementations, projectable transaction card 210 may beconfigured to communicate directly with user device 230 and/or entitylocation device 240. In some implementations, projectable transactioncard 210 may transmit and/or receive information over network 250. Insome implementations, projectable transaction card 210 may use one orboth of user device 230 or entity location device 240 to communicateover network 250. For example, projectable transaction card 210 mayprovide information that identifies a location of projectabletransaction card 210 to user device 230 for transmission to navigationdevice 220. Additionally, or alternatively, projectable transaction card210 may receive information, such as navigation information, fromnavigation device 220 via user device 230.

Navigation device 220 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith determining and/or providing navigation information for navigatingfrom a location associated with projectable transaction card 210 to alocation associated with an account entity. For example, navigationdevice 220 may include a server device (e.g., a host server, a webserver, an application server, etc.), a data center device, a cloudcomputing device in a cloud computing environment, or a similar device.In some implementations, navigation device 220 may receive informationthat identifies a location of a projectable transaction card 210, accessinformation that identifies a location associated with the accountentity, and determine information for navigating from the location ofprojectable transaction card 210 to the location associated with theaccount entity. In some implementations, navigation device 220 maydetermine the information for navigating based on providing informationregarding the locations to another device and receiving the informationfor navigating from the other device.

In some implementations, navigation device 220 may determine whether toprovide the navigation information to projectable transaction card 210based on whether projectable transaction card 210 is in proximity to thelocation associated with the account entity. Navigation device 220 maymake this determination before or after determining the information fornavigating from the location of the location of projectable transactioncard 210 to the location associated with the account entity. In someimplementations, the information for navigating may be used as a basisfor providing the navigation information.

User device 230 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith navigation device 220 providing navigation information toprojectable transaction card 210. For example, user device 230 mayinclude a communication and/or computing device, such as a mobile phone(e.g., a smart phone, a radiotelephone, etc.), a laptop computer, atablet computer, a handheld computer, a desktop computer, a gamingdevice, a wearable communication device (e.g., a smart wristwatch, apair of smart eyeglasses, etc.), or a similar type of device.

Entity location device 240 includes one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with determining and/or providing navigation information fornavigating from a location associated with projectable transaction card210 to a location associated with an account entity. For example, entitylocation device 240 may include a communication and/or computing device,such as a mobile phone (e.g., a smart phone, a radiotelephone, etc.), alaptop computer, a tablet computer, a handheld computer, a desktopcomputer, a server device (e.g., a host server, a web server, anapplication server, etc.), and/or the like.

Entity location device 240 may communicate with one or more ofprojectable transaction card 210, user device 230, or navigation device220. In some implementations, entity location device 240 may provideinformation, such as information that identifies a location of one ormore locations associated with the account entity. In someimplementations, entity location device 240 may be positioned within oneor more locations associated with the account entity (e.g., at alocation including a branch of a financial institution).

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, and/or the like), a public land mobile network(PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, and/or the like, and/or a combination of these orother types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as one or more examples. In practice, there may be additionaldevices and/or networks, fewer devices and/or networks, differentdevices and/or networks, or differently arranged devices and/or networksthan those shown in FIG. 2 . Furthermore, two or more devices shown inFIG. 2 may be implemented within a single device, or a single deviceshown in FIG. 2 may be implemented as multiple, distributed devices.Additionally, or alternatively, a set of devices (e.g., one or moredevices) of environment 200 may perform one or more functions describedas being performed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to projectable transaction card 210, navigation device220, user device 230, and/or entity location device 240. In someimplementations, projectable transaction card 210, navigation device220, user device 230, and/or entity location device 240 may include oneor more devices 300 and/or one or more components of device 300. Asshown in FIG. 3 , device 300 may include a bus 310, a processor 320, amemory 330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among multiplecomponents of device 300. Processor 320 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 320is a central processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, and/or amagneto-optic disk), a solid state drive (SSD), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 360 includes a component thatprovides output information from device 300 (via, e.g., a display, aspeaker, a haptic feedback component, an audio or visual indicator,and/or the like).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver, a separate receiver, a separate transmitter, and/or thelike) that enables device 300 to communicate with other devices, such asvia a wired connection, a wireless connection, or a combination of wiredand wireless connections. Communication interface 370 may permit device300 to receive information from another device and/or provideinformation to another device. For example, communication interface 370may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a Wi-Fi interface, a cellularnetwork interface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. As used herein,the term “computer-readable medium” refers to a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardware circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3 . Additionally, or alternatively,a set of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flowchart of an example process 400 for account entitylocation based navigation and display for a projectable transactioncard. In some implementations, one or more process blocks of FIG. 4 maybe performed by a device (e.g., navigation device 220). In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including thenavigation device, such as a user device or entity location device(e.g., user device 230 or entity location device 240), and/or the like.

As shown in FIG. 4 , process 400 may include determining informationthat identifies a location of a projectable transaction card, whereinthe projectable transaction card is associated with an account entityand wherein the projectable transaction card is associated with a useraccount associated with the account entity (block 410). For example, thedevice (e.g., using processor 320, memory 330, storage component 340,input component 350, output component 360, communication interface 370and/or the like) may determine information that identifies a location ofa projectable transaction card, as described above. In someimplementations, the projectable transaction card is associated with anaccount entity. In some implementations, the projectable transactioncard is associated with a user account associated with the accountentity.

As further shown in FIG. 4 , process 400 may include determining thatthe location of the projectable transaction card is in proximity to alocation associated with the account entity (block 420). For example,the device (e.g., using processor 320, memory 330, storage component340, input component 350, output component 360, communication interface370 and/or the like) may determine that the location of the projectabletransaction card is in proximity to a location associated with theaccount entity, as described above.

As further shown in FIG. 4 , process 400 may include determiningnavigation information based on determining that the location of theprojectable transaction card is in proximity to the location associatedwith the account entity, wherein the navigation information includesinformation for navigating from the location of the projectabletransaction card to the location associated with the account entity(block 430). For example, the device (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may determine navigationinformation based on determining that the location of the projectabletransaction card is in proximity to the location associated with theaccount entity, as described above. In some implementations, thenavigation information includes information for navigating from thelocation of the projectable transaction card to the location associatedwith the account entity.

As further shown in FIG. 4 , process 400 may include providing thenavigation information for display on a display screen of theprojectable transaction card, wherein the navigation information is notprovided for display on the display screen of the projectabletransaction card prior to the location of the projectable transactioncard being in proximity to the location associated with the accountentity (block 440). For example, the device (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370 and/or the like) may provide thenavigation information for display on a display screen of theprojectable transaction card, as described above. In someimplementations, the navigation information is not provided for displayon the display screen of the projectable transaction card prior to thelocation of the projectable transaction card being in proximity to thelocation associated with the account entity.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, process 400 further comprises determining atype of the location associated with the account entity and identifyingthe type of the location associated with the account entity as anunfiltered location type, wherein providing the navigation informationfor display on the display screen of the projectable transaction cardcomprises providing the navigation information for display further basedon identifying the type of the location associated with the accountentity as an unfiltered location type.

In a second implementation, alone or in combination with the firstimplementation, process 400 further comprises determining that thelocation of the projectable transaction card is within a thresholddistance of the location associated with the account entity, whereindetermining that the location of the projectable transaction card is inproximity to the location associated with the account entity comprisesdetermining that the location of the projectable transaction card is inproximity to the location associated with the account entity based ondetermining that the location of the projectable transaction card iswithin the threshold distance of the location associated with theaccount entity.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, process 400 further comprisesdetermining that the location of the projectable transaction card iswithin a geographical area associated with the account entity, whereindetermining that the location of the projectable transaction card is inproximity to the location associated with the account entity comprisesdetermining that the location of the projectable transaction card is inproximity to the location associated with the account entity based ondetermining that the location of the projectable transaction card iswithin the geographical area associated with the account entity.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, process 400 further comprisesproviding, for display, a user interface associated with whether todisplay the navigation information and receiving, based on user inputprovided via the user interface, an indication that the navigationinformation is to be displayed, wherein providing the navigationinformation for display on the display screen of the projectabletransaction card comprises providing the navigation information fordisplay further based on the indication that the navigation informationis to be displayed.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, process 400 further comprisesdetermining that an upcoming due date, associated with the user account,is within a time threshold, wherein providing the navigation informationfor display on the display screen of the projectable transaction cardcomprises providing the navigation information for display further basedon determining that the upcoming due date is within the time threshold.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, process 400 further comprisesdetermining historical activity information associated with the useraccount and determining, based on the historical activity information,that activity associated with the user account is expected, whereinproviding the navigation information for display on the display screenof the projectable transaction card comprises providing the navigationinformation for display further based on determining that the activityassociated with the user account is expected.

In a seventh implementation, alone or in combination with one or more ofthe first through sixth implementations, process 400 further comprisesdetermining information that identifies an updated location of theprojectable transaction card, determining that the updated location ofthe projectable transaction card is not in proximity to the locationassociated with the account entity, and causing the navigationinformation to stop being displayed on the display screen of theprojectable transaction card based on determining that the updatedlocation of the projectable transaction card is not in proximity to thelocation associated with the account entity.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for account entitylocation based navigation and display for a projectable transactioncard. In some implementations, one or more process blocks of FIG. 5 maybe performed by a device (e.g., navigation device 220). In someimplementations, one or more process blocks of FIG. 5 may be performedby another device or a group of devices separate from or including thenavigation device, such as a user device or entity location device(e.g., user device 230 or entity location device 240), and/or the like.

As shown in FIG. 5 , process 500 may include identifying a location of aprojectable transaction card associated with an account entity, whereinthe projectable transaction card is associated with a user accountassociated with the account entity (block 510). For example, the device(e.g., using processor 320, memory 330, storage component 340, inputcomponent 350, output component 360, communication interface 370 and/orthe like) may identify a location of a projectable transaction cardassociated with an account entity, as described above. In someimplementations, the projectable transaction card is associated with auser account associated with the account entity.

As further shown in FIG. 5 , process 500 may include determining thatthe location of the projectable transaction card is within at least oneof: a threshold distance of a location associated with the accountentity, or a geographical area associated with the location of theaccount entity (block 520). For example, the device (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370 and/or the like) maydetermine that the location of the projectable transaction card iswithin a threshold distance of a location associated with the accountentity and/or a geographical area associated with the location of theaccount entity, as described above.

As further shown in FIG. 5 , process 500 may include determiningnavigation information for navigating from the location of theprojectable transaction card to the location associated with the accountentity, wherein the navigation information is determined based on thelocation of the projectable transaction card being within the thresholddistance or within the geographical area (block 530). For example, thedevice (e.g., using processor 320, memory 330, storage component 340,input component 350, output component 360, communication interface 370and/or the like) may determine navigation information for navigatingfrom the location of the projectable transaction card to the locationassociated with the account entity, as described above. In someimplementations, the navigation information may be determined based onthe location of the projectable transaction card being within thethreshold distance or within the geographical area.

As further shown in FIG. 5 , process 500 may include providing thenavigation information for display on a display screen of theprojectable transaction card, wherein the navigation information is notprovided for display on the display screen of the projectabletransaction card prior to the location of the projectable transactioncard being within the threshold distance or within the geographical area(block 540). For example, the device (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may provide the navigationinformation for display on a display screen of the projectabletransaction card, as described above. In some implementations, thenavigation information is not provided for display on the display screenof the projectable transaction card prior to the location of theprojectable transaction card being within the threshold distance orwithin the geographical area.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the one or more processors are furtherconfigured to determine a type of the location associated with theaccount entity and identify the type of the location associated with theaccount entity as an unfiltered location type, wherein the one or moreprocessors, when providing the navigation information for display on thedisplay screen of the projectable transaction card, are configured toprovide the navigation information for display further based onidentifying the type of the location associated with the account entityas an unfiltered location type.

In a second implementation, alone or in combination with the firstimplementation, the one or more processors are further configured toprovide, for display, a user interface associated with whether todisplay the navigation information and receive, based on user inputprovided via the user interface, an indication that the navigationinformation is to be displayed, and wherein the one or more processors,when providing the navigation information for display on the displayscreen of the projectable transaction card, are configured to providethe navigation information for display further based on the indicationthat the navigation information is to be displayed.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the one or more processors arefurther configured to determine that an upcoming due date, associatedwith the user account, is within a time threshold, and wherein the oneor more processors, when providing the navigation information fordisplay on the display screen of the projectable transaction card, areconfigured to provide the navigation information for display furtherbased on determining that the upcoming due date is within the timethreshold.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the one or more processors arefurther configured to determine historical activity informationassociated with the user account and determine, based on the historicalactivity information, that activity associated with the user account isexpected, and wherein the one or more processors, when providing thenavigation information for display on the display screen of theprojectable transaction card, are configured to provide the navigationinformation for display further based on determining that the activityassociated with the user account is expected.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the one or more processors arefurther configured to determine information that identifies an updatedlocation of the projectable transaction card, determine that the updatedlocation of the projectable transaction card is not within the thresholddistance or within the geographical area of the location associated withthe account entity, and cause the navigation information to stop beingdisplayed on the display screen of the projectable transaction cardbased on determining that the updated location of the projectabletransaction card is not within the threshold distance or thegeographical area of the location associated with the account entity.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for account entitylocation based navigation and display for a projectable transactioncard. In some implementations, one or more process blocks of FIG. 6 maybe performed by a device (e.g., navigation device 220). In someimplementations, one or more process blocks of FIG. 6 may be performedby another device or a group of devices separate from or including thenavigation device, such as a user device or entity location device(e.g., user device 230 or entity location device 240), and/or the like.

As shown in FIG. 6 , process 600 may include determining that a locationof a projectable transaction card is in proximity to a locationassociated with an account entity, wherein the projectable transactioncard is associated with the account entity, and wherein the projectabletransaction card is associated with a user account associated with theaccount entity (block 610). For example, the device (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370 and/or the like) maydetermine that a location of a projectable transaction card is inproximity to a location associated with an account entity, as describedabove. In some implementations, the projectable transaction card isassociated with the account entity. In some implementations, theprojectable transaction card is associated with a user accountassociated with the account entity.

As further shown in FIG. 6 , process 600 may include determiningnavigation information based on determining that the location of theprojectable transaction card is in proximity to the location associatedwith the account entity, wherein the navigation information includesinformation for navigating from the location of the projectabletransaction card to the location associated with the account entity(block 620). For example, the device (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may determine navigationinformation based on determining that the location of the projectabletransaction card is in proximity to the location associated with theaccount entity, as described above. In some implementations, thenavigation information includes information for navigating from thelocation of the projectable transaction card to the location associatedwith the account entity.

As further shown in FIG. 6 , process 600 may include providing thenavigation information for display on a display screen of theprojectable transaction card, wherein the navigation information is notprovided for display on the display screen of the projectabletransaction card prior to the location of the projectable transactioncard being in proximity to the location associated with the accountentity (block 630). For example, the device (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370 and/or the like) may provide thenavigation information for display on a display screen of theprojectable transaction card, as described above. In someimplementations, the navigation information is not provided for displayon the display screen of the projectable transaction card prior to thelocation of the projectable transaction card being in proximity to thelocation associated with the account entity.

Process 600 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the one or more instructions, when executedby the one or more processors, further cause the one or more processorsto determine a type of the location associated with the account entityand identify the type of the location associated with the account entityas an unfiltered location type, and wherein the one or moreinstructions, that cause the one or more processors to provide thenavigation information for display on the display screen of theprojectable transaction card, cause the one or more processors toprovide the navigation information for display further based onidentifying the type of the location associated with the account entityas an unfiltered location type.

In a second implementation, alone or in combination with the firstimplementation, the one or more instructions, when executed by the oneor more processors, further cause the one or more processors todetermine that the location of the projectable transaction card iswithin at least one of a threshold distance of the location associatedwith the account entity, or a geographical area associated with thelocation associated with the account entity, and wherein the one or moreinstructions, that cause the one or more processors to determine thatthe location of the projectable transaction card is in proximity to thelocation associated with the account entity, cause the one or moreprocessors to determine that the location of the projectable transactioncard is in proximity to the location associated with the account entitybased on determining that the location of the projectable transactioncard is within the threshold distance or within the geographical area.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the one or more instructions, whenexecuted by the one or more processors, further cause the one or moreprocessors to provide, for display, a user interface associated withwhether to display the navigation information and receive, based on userinput provided via the user interface, an indication that the navigationinformation is to be displayed, and wherein the one or moreinstructions, that cause the one or more processors to provide thenavigation information for display on the display screen of theprojectable transaction card, cause the one or more processors toprovide the navigation information for display further based on theindication that the navigation information is to be displayed.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to determine that an upcoming due date, associated withthe user account, is within a time threshold, and wherein the one ormore instructions, that cause the one or more processors to provide thenavigation information for display on the display screen of theprojectable transaction card, cause the one or more processors toprovide the navigation information for display further based ondetermining that the upcoming due date is within the time threshold.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to determine historical activity information associatedwith the user account and determine, based on the historical activityinformation, that activity associated with the user account is expected,and wherein the one or more instructions, that cause the one or moreprocessors to provide the navigation information for display on thedisplay screen of the projectable transaction card, cause the one ormore processors to provide the navigation information for displayfurther based on determining that the activity associated with the useraccount is expected.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6 . Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, and/or the like.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, and/or thelike. A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems and/or methods is notlimiting of the implementations. Thus, the operation and behavior of thesystems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” and/or the likeare intended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: transmitting, by aprojectable transaction card, location information to a device, whereinthe projectable transaction card includes a transaction card thatincludes a display screen on the transaction card; wherein theprojectable transaction card is associated with an account entity, andwherein the location information is associated with a location of theprojectable transaction card; receiving, by the projectable transactioncard and from the device and based on the location of the projectabletransaction card being in proximity to a location associated with theaccount entity, navigation information for display on the display screenof the projectable transaction card, wherein the navigation informationis determined to be provided by the device based on a pattern of accountactivity determined from historical account activity, and wherein thenavigation information includes directions for navigating from thelocation of the projectable transaction card to the location associatedwith the account entity; and providing, for display by the projectabletransaction card, the navigation information via the display screen ofthe projectable transaction card, wherein the navigation information isnot provided for display on the display screen of the transaction cardprior to the location of the projectable transaction card being inproximity to the location associated with the account entity.
 2. Themethod of claim 1, wherein the navigation information is displayed asone or more of: one or more alphanumeric characters, a map, or one ormore symbols.
 3. The method of claim 1, further comprising: receivingupdated location information associated with an updated location of theprojectable transaction card; and preventing the display screen fromproviding the navigation information.
 4. The method of claim 1, whereinproviding the navigation information via the display screen is based ona determination that the projectable transaction card is within athreshold distance of the location associated with the account entity.5. The method of claim 1, wherein the display screen is configured toadditionally display one or more of: an account identifier associatedwith the projectable transaction card, a transaction indicatorassociated with the projectable transaction card, or a name of anaccount holder associated with the projectable transaction card.
 6. Themethod of claim 1, wherein transmitting the location information isbased on a user interaction with the projectable transaction card. 7.The method of claim 1, wherein the projectable transaction card isconfigured with an identification of the location associated with theaccount entity, and further comprising: detecting that the projectabletransaction card is within a threshold distance of the locationassociated with the account entity based on the configuration, andwherein transmitting the location is based on the detection that theprojectable transaction is within the threshold distance of the locationassociated with the account entity.
 8. A projectable transaction card,comprising: one or more memories; and one or more processors, coupled tothe one or more memories, configured to: transmit location informationto a device, wherein the projectable transaction card is associated withan account entity, wherein the projectable transaction card includes atransaction card that includes a display screen on the transaction card,and wherein the location information is associated with a location ofthe projectable transaction card; receive, from the device and based onthe location of the projectable transaction card being in proximity to alocation associated with the account entity, navigation information fordisplay on the display screen of the projectable transaction card,wherein the navigation information is determined to be provided by thedevice based on a pattern of account activity determined from historicalaccount activity, and wherein the navigation information includesdirections for navigating from the location of the projectabletransaction card to the location associated with the account entity; andprovide, for display by the projectable transaction card, the navigationinformation via the display screen of the projectable transaction card,wherein the navigation information is not provided for display on thedisplay screen of the projectable transaction card prior to the locationof the transaction card being in proximity to the location associatedwith the account entity.
 9. The projectable transaction card of claim 8,wherein the navigation information is displayed as one or more of: oneor more alphanumeric characters, a map, or one or more symbols.
 10. Theprojectable transaction card of claim 8, wherein the one or moreprocessors are further configured to: receive updated locationinformation associated with an updated location of the projectabletransaction card; and prevent the display screen from providing thenavigation information.
 11. The projectable transaction card of claim 8,wherein the one or more processors, when providing the navigationinformation via the display screen, are configured to: provide thenavigation information based on a determination that the projectabletransaction card is within a threshold distance of the locationassociated with the account entity.
 12. The projectable transaction cardof claim 8, wherein the display screen is configured to additionallydisplay one or more of: an account identifier associated with theprojectable transaction card, a transaction indicator associated withthe projectable transaction card, or a name of an account holderassociated with the projectable transaction card.
 13. The projectabletransaction card of claim 8, wherein the one or more processors, whentransmitting the location information, are configured to: transmit thelocation information based on a user interaction with the projectabletransaction card.
 14. The projectable transaction card of claim 8,wherein the projectable transaction card is configured with anidentification of the location associated with the account entity, andwherein the one or more processors are configured to: detect that theprojectable transaction card is within a threshold distance of thelocation associated with the account entity based on the configuration,and wherein the one or more processors, when transmitting the location,are configured to: transmit the location based on the detection that theprojectable transaction is within the threshold distance of the locationassociated with the account entity.
 15. A non-transitorycomputer-readable medium storing a set of instructions, the set ofinstructions comprising: one or more instructions that, when executed byone or more processors of a projectable transaction card, cause theprojectable transaction card to: transmit location information to adevice, wherein the projectable transaction card is associated with anaccount entity, wherein the projectable transaction card includes atransaction card that includes a display screen on the transaction card,and wherein the location information is associated with a location ofthe projectable transaction card; receive, from the device and based onthe location of the projectable transaction card being in proximity to alocation associated with the account entity, navigation information fordisplay on the display screen of the projectable transaction card,wherein the navigation information includes directions for navigatingfrom the location of the projectable transaction card to the locationassociated with the account entity; and provide, for display by theprojectable transaction card, the navigation information via the displayscreen of the projectable transaction card, wherein the navigationinformation is not provided for display on the display screen of theprojectable transaction card prior to the location of the transactioncard being in proximity to the location associated with the accountentity, and wherein the one or more instructions, that cause theprojectable transaction card to provide the navigation information viathe display screen, cause the projectable transaction card to: providethe navigation information based on a determination that the projectabletransaction card is within a threshold distance of the locationassociated with the account entity,  wherein the threshold distance isdetermined by the device based on at least one of historical activityinformation associated with a user account or historical locationinformation associated with the projectable transaction card.
 16. Thenon-transitory computer-readable medium of claim 15, wherein thenavigation information is displayed as one or more of: one or morealphanumeric characters, a map, or one or more symbols.
 17. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions further cause the projectable transaction card to:receive updated location information associated with an updated locationof the projectable transaction card; and prevent the display screen fromproviding the navigation information.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, wherein the navigation information is determined to beprovided by the device based a pattern of account activity determinedfrom historical account activity.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions further cause the projectable transaction card toadditionally display one or more of: an account identifier associatedwith the projectable transaction card, a transaction indicatorassociated with the projectable transaction card, or a name of anaccount holder associated with the projectable transaction card.
 20. Thenon-transitory computer-readable medium of claim 15, wherein theprojectable transaction card is configured with local access to a set ofmaps associated with the location information associated with theaccount entity.